Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1600

reference
503-tree-1
name
1600
tree-preservation-order

undefined

503-tpo-1
uprn
address-text
point
POINT (-1.037332 50.886354)
geometry
MULTIPOLYGON (((-1.037261 50.886346,-1.037264 50.886360,-1.037274 50.886373,-1.037289 50.886383,-1.037309 50.886390,-1.037331 50.886392,-1.037353 50.886390,-1.037373 50.886384,-1.037389 50.886374,-1.037399 50.886361,-1.037403 50.886348,-1.037400 50.886334,-1.037390 50.886321,-1.037374 50.886311,-1.037355 50.886304,-1.037333 50.886302,-1.037311 50.886304,-1.037291 50.886310,-1.037275 50.886320,-1.037264 50.886333,-1.037261 50.886346)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL